Google Links

Follow the links below to find material targeted to the unit's elements, performance criteria, required skills and knowledge

Elements and Performance Criteria

1. Determine the functional changes required
   • Consult the user to determine, and document, the functional change required
   • Clarify the impact of changes with operational personnel
2. Review legacy language
   • Identify the basic structures of the legacy language
   • Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling
   • Review the basic algorithms of the legacy language
3. Identify and isolate the change
   • Review the technical documentation for the system, to determine which modules to change
   • Review the source code to determine program logic and flow
   • Update the technical documentation to reflect the current state of the program
4. Determine the framework for change
   • Determine the change approach to be used to implement the change
   • Ascertain and detail the risks for each approach
   • Determine the personnel who will make the changes
5. Design the change
   • Develop the changes required, considering the impact of the changes on other parts of the system
   • Document the changes according to change-management standards
6. Code the change
   • Identify and obtain, the appropriate hardware and software for the change
   • Write the code according to programming standards
   • Compile and unit test the changes
   • Document the changes according to programming standards
7. Test the change
   • System test the changes and record the outcomes
   • Perform user acceptance testing and record the outcomes
   • Sign off the change request
8. Archive the system
   • Create a new version of software, according to configuration management standards
   • Archive the development system, including the source code, compilers and test data

Performance Evidence

Evidence of the ability to:

read legacy language

identify and isolate the required change

implement the change via the chosen technique.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

---

Knowledge Evidence

To complete the unit requirements safely and effectively, the individual must:

explain operational procedures on the required operating system

outline the organisational standards for software development

define security and viruses

identify privacy legislation and copyright with regard to the legacy code, the particular system involved and its data

define the technical terminology related to reading help files and manuals

outline different types of software.

---